- Add comprehensive test for webpack worker compilation with Module Federation
- Test verifies worker syntax new Worker(new URL()) compiles correctly
- Validates federated modules (React, ComponentA) are accessible in worker context
- Tests both CommonJS (async-node) and ESM (node14) module outputs
- Provides URL to test scope via moduleScope for Node.js targets
- All 10 tests pass successfully (5 tests × 2 builds)

Added beforeEach hook to reset React version to '0.1.2' before running worker tests.
This prevents test contamination from other container tests (like 1-container-full)
that set React version to '3.2.1' and cause the worker test to fail with unexpected
version mismatches.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

… cross-context relocation

Enhanced runtime chunk detection and federation runtime injection to properly support worker
threads. Added safeguards to prevent runtime module relocation between different execution
contexts (main thread vs workers).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

…e:pkg)

…tern

…ker demo

- Enable runtimeChunk in webpack config to ensure bundler runtime is available
- Update WorkerDemo to use WorkerWrapper instead of module worker
- This fixes the 'bundler runtime is required to load remote chunk' error in workers

…ndencies in workers

Changed EmbedFederationRuntimeModule to use stage 40 (higher than STAGE_TRIGGER=20)
to ensure it wraps __webpack_require__.x AFTER StartupChunkDependenciesRuntimeModule.

This fixes the issue where workers failed with "Cannot read properties of undefined
(reading 'remotes')" because the federation runtime wasn't initialized before the
remotes handler was invoked.

The execution order is now:
1. StartupChunkDependencies wraps __webpack_require__.x (stage 20)
2. EmbedFederation wraps it again (stage 40)
3. When called: EmbedFederation → init runtime → StartupChunkDependencies → load chunks

Also added logging to track execution flow and suppressed async/await warnings
in webpack config.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

…tion fix

Added and updated tests to verify the stage 40 fix for EmbedFederationRuntimeModule:

- Updated FederationRuntimePluginWorkerRuntime.test.ts to verify runtime module
  execution order in worker bundles (EmbedFederation appears AFTER StartupChunkDependencies)
- Updated FederationRuntimePluginHostRuntime.test.ts to add test for main bundle
  generation with correct runtime module order
- Created HoistContainerReferencesPlugin.test.ts with 13 comprehensive tests covering:
  - Plugin application and hook registration
  - Runtime chunk detection
  - Module hoisting for container entries, federation runtime, and worker runtime
  - Chunk cleanup
  - getAllReferencedModules helper function with various traversal types
- Updated RemoteRuntimeModule.test.ts to include defensive initialization lines

All 632 tests passing.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

…rder

Refactored both FederationRuntimePlugin compiler-unit tests to use
programmatic webpack execution instead of spawning webpack-cli:

- FederationRuntimePluginHostRuntime.test.ts:
  - Removed swc-loader dependency by using plain JavaScript
  - Changed to use programmatic webpack API (runWebpack helper)
  - Adjusted first test to expect successful build (not error)
  - Changed second test to use development mode to preserve markers
  - Updated assertions to check for actual functional code

- FederationRuntimePluginWorkerRuntime.test.ts:
  - Fixed ROOT path calculation (was off by one level)

All tests now pass successfully.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Fixed FederationRuntimePluginWorkerRuntime.test.ts by:
- Removed `plugin._options.remotes = {}` which was causing module resolution errors
- Fixed collectInfrastructureErrors to handle non-iterable entries properly
- Simplified error checking to log errors for debugging

The test was failing because it removed all remotes, but the source code
imports from remote1 modules (WebpackSvg, WebpackPng, useCustomRemoteHook).
The build now succeeds by keeping the remotes configuration intact.

All 73 container tests now pass.

Fixed Next.js e2e tests failing with "__webpack_require__.f is undefined" by
changing the execution order in EmbedFederationRuntimeModule:

**Before:**
1. Require federation entry
2. Call prevStartup()

**After:**
1. Call prevStartup() - initializes webpack runtime handlers
2. Require federation entry - handlers are now available

The federation entry imports modules that depend on webpack runtime handlers
like __webpack_require__.f.consumes. By calling prevStartup first, we ensure
all these handlers are registered before the federation entry is required.

This fixes the error:
"Cannot read properties of undefined (reading 'consumes')"
at __webpack_require__.f.consumes

Also changed stage from 40 to 30 to run earlier in the initialization sequence
while still being after StartupChunkDependenciesRuntimeModule (stage 20).

Changes:
- Simplified EmbedFederationRuntimeModule to load federation entry at STAGE_NORMAL
- Removed stub bundlerRuntime approach (caused merging issues with prevFederation)
- Updated Cypress configs to use CI env variable for retry logic (0 locally, 2-3 in CI)
- Created run-next-e2e.mjs script for local Next.js e2e testing
- Added RUNTIME_INIT_FIX.md documentation explaining the stage ordering issue
- Deleted unused ChildCompilationRuntimePlugin.ts

Known Issue: Next.js SSR still has 500 errors during page rendering.
The federation entry loads correctly in client bundles but server bundles may need investigation.

🤖 Generated with Claude Code
https://claude.com/claude-code

Co-Authored-By: Claude <[email protected]>

…tialization

Fixes worker runtime initialization while maintaining Next.js compatibility by
detecting chunk loading type and applying appropriate runtime module stages.

- JSONP chunks (Next.js): STAGE_ATTACH (10) - loads inside startup hook
- Worker chunks (import-scripts): STAGE_BASIC (5) - loads immediately before RemoteRuntimeModule
- Follows webpack's pattern from JsonpChunkLoadingPlugin for chunk type detection
- Adds comprehensive unit tests for stage selection logic

Resolves initialization timing issues where bundlerRuntime was undefined when
RemoteRuntimeModule tried to access it in worker environments.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

… pattern

Updates FederationRuntimePluginWorkerRuntime test to reflect the new
implementation where worker chunks use immediate execution (stage 5)
instead of startup hook wrapper pattern.

- Removes checks for old startup hook pattern (prevStartup wrapper)
- Verifies federation runtime module is present
- Validates federation entry is loaded regardless of execution pattern

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>